TwinTurbo.NET: Nissan 300ZX forum - I was going to call you later.
People Seeking Info
 
   


     
Subject I was going to call you later.
     
Posted by DVDBURN (MD) on September 05, 2011 at 11:07 AM
  This message has been viewed 302 times.
     
In Reply To Yeah it is a pecularity in the stock tune. (n/m) posted by ztunerz on September 05, 2011 at 09:37 AM
     
Message While doing all this, I found a very interesting relationship between the actual byte value, the TP and the RPM in how they are calculated in order to get their significant (displayed and used) values.

Example...and this applies to both the fuel and timing values. I'll use a timing value example to make it easier.

A byte in the bin (timing map) with a value of 154 is calculated to be displayed as 26 degrees.

A byte in the bin (timing map) with a value of 26 is displayed just as that, 26 degrees.

I found that this can occur with any number but that the placement of the number (I.E. 26 or 154) depends on which part of the map it is placed depending on the TP and RPM values. It all has to do with the way the micro is accessing data via the 0-255 scale.

Now this is what is also interesting. JWT moves the lower TP values to the far right so that all byte values in the map are a lower constant value.

The calculated higher (byte) values are dependant on where the TPs and RPMs are at. Notice they're absent after 3000rpm and under 44tp ?

Here are couple of pictures to try to explain.

Anything behind the L (to the left of the TP and higher in RPM) is a "hole number sort of speak" in it's byte value. Anything in the H area is a higher number that needs to be calculated down in order to display it's significant displayed number. The thing that's interesting is that the programming in the micro ramps up in 0-255 scale and needs to read those higher numbers in that area for the reason of TP vs RPM.

Now, like I said, JWT will move the TP at 44 to the far right (doing away with all other TP values) and keep all numbers in the map L's (lower).

Luckily I caught this and created routines to advance or reduce any byte number (value) that might be in any cell of the map regardless of whether it's a high or a low value.

I think understanding this is pertinent to any tuning software because you could always go with any lower number to get the same displayed significant result. But! how would the micro handle it???

www.mytwinturbo.com

Nissan Data Voice - The first Nissan diagnostic software with a voice!

Download my Nissan 300ZX Vin/Model Lookup.

Watch an ECZA meet caravan!

     
Follow Ups  
     
Post a
Followup

You cannot reply to this message because you are not logged in.